Skip to content

update umbra and add umbra s3#951

Open
toschmidt wants to merge 1 commit into
ClickHouse:mainfrom
umbra-db:schmidt/umbra26.06
Open

update umbra and add umbra s3#951
toschmidt wants to merge 1 commit into
ClickHouse:mainfrom
umbra-db:schmidt/umbra26.06

Conversation

@toschmidt

@toschmidt toschmidt commented Jun 19, 2026

Copy link
Copy Markdown
Contributor

Updates Umbra and improves runtimes by loading the data from parquet and using compression.

This also resolves the memory usage problem on smaller instances reported in #543 and the infinite loop during the concurrent measurements in #891.

Add a new Umbra variant that stores the data on S3 instead of the EBS device. Similar to ClickHouse (web), which also uses S3 as a storage backend.

@toschmidt
toschmidt force-pushed the schmidt/umbra26.06 branch from f18517e to 0c1d4b1 Compare June 22, 2026 11:17
@toschmidt toschmidt changed the title update umbra update umbra and add umbra s3 Jun 22, 2026
@rschu1ze rschu1ze self-assigned this Jun 30, 2026

@rschu1ze rschu1ze left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@toschmidt I get a permission denied error when I try to push to this PR.

/data/ClickBench (schmidt/umbra26.06 >) $ git push umbra schmidt/umbra26.06
remote: Permission to umbra-db/ClickBench.git denied to rschu1ze.
fatal: unable to access 'https://github.com/umbra-db/ClickBench.git/': The requested URL returned error: 403

Could I ask you to merge from main and resolve the conflicts?

Comment thread umbra/create.sql
Comment thread umbra/create.sql
Comment thread umbra/create.sql Outdated
Comment thread umbra/start
Comment thread umbra/start
@toschmidt
toschmidt force-pushed the schmidt/umbra26.06 branch 3 times, most recently from aaada50 to f0fc7c9 Compare July 14, 2026 07:26
@thevar1able thevar1able self-assigned this Jul 15, 2026
@rschu1ze rschu1ze removed their assignment Jul 15, 2026
@alexey-milovidov

Copy link
Copy Markdown
Member

Could you please allow pushes to your branch? It will be needed for the automation.
Or just merge the latest main, which includes the required automation.

@toschmidt
toschmidt force-pushed the schmidt/umbra26.06 branch from f0fc7c9 to 29ed04f Compare July 22, 2026 17:41
@toschmidt
toschmidt temporarily deployed to benchmark-approval July 22, 2026 17:42 — with GitHub Actions Inactive
@toschmidt

Copy link
Copy Markdown
Contributor Author

Could you please allow pushes to your branch? It will be needed for the automation. Or just merge the latest main, which includes the required automation.

I rebased the branch, but I can't enable edits from maintainers. The fork is owned by an organization, and apparently GitHub does not support this option (https://github.com/orgs/community/discussions/5634). I can add you guys to our fork to allow edits, or do you know another way?

@github-actions

Copy link
Copy Markdown
Contributor

Results for umbra are ready for: c6a.4xlarge.
This pull request is from a fork, so the automation cannot push to it; save this result as umbra/results/20260722/c6a.4xlarge.json.
Tick "Allow edits by maintainers" on the pull request to let the automation commit the results itself.
The run of umbra-s3 on c6a.4xlarge did not produce results.

Logs:

@alexey-milovidov

Copy link
Copy Markdown
Member

Umbra works, but Umbra S3 doesn't.

@rschu1ze

Copy link
Copy Markdown
Member

The problem is that the S3 variant requires a static AWS access key to reproduce results. We can use our own but it will leak somewhere in publicly available log files (like here).

Would it be possible to omit -s3 for now?

@toschmidt

Copy link
Copy Markdown
Contributor Author

Yes, we can omit umbra-s3. It's possible to run it manually, the Readme contains details how to create and destroy the S3 bucket. For an automated run, I would not enable it as the bucket could be leaked and it requires permissions to create buckets in ec2 instance.

Do you want to remove it entirely or just exclude from the automated benchmarks?

Update the Umbra ClickBench definition: drop the primary key, ingest from
the Athena hits.parquet via the umbra.parquetview table function (instead
of a TSV COPY), and store the table with zstd compression (create.sql, the
Docker variant, reads /data/hits.parquet from the bind mount).

Switch the dataset download to hits.parquet (BENCH_DOWNLOAD_SCRIPT) to
match, require the loaded row count to equal exactly 99,997,497 (a partial
load otherwise sails through with implausibly fast timings on the
surviving subset), and run the Docker container --privileged.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@toschmidt
toschmidt force-pushed the schmidt/umbra26.06 branch from 29ed04f to cc913e1 Compare July 23, 2026 00:41
@toschmidt
toschmidt requested a deployment to benchmark-approval July 23, 2026 00:41 — with GitHub Actions Waiting
@toschmidt

Copy link
Copy Markdown
Contributor Author

I removed umbra-s3 and will do a follow up pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants